Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8cf9891261d13bf3aaaf6779c7391e2f2c9f94c8b39e8e8c8b7c80501525697c

Tx prefix hash: 0af522df30a6541bcba9578b4495d1c182fdc2dba487f983014b77b415e90370
Tx public key: 0a3308db4afd8035b0e760b10191ad1b067e342b66aa96cd752daa1f1eaa5534
Timestamp: 1588737265 Timestamp [UCT]: 2020-05-06 03:54:25 Age [y:d:h:m:s]: 05:156:17:24:42
Block: 99131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1286570 RingCT/type: yes/0
Extra: 010a3308db4afd8035b0e760b10191ad1b067e342b66aa96cd752daa1f1eaa553402110000000239be35fb000000000000000000

1 output(s) for total of 288.096915764000 dcy

stealth address amount amount idx
00: 2e12c22c120d256627725daeb3899e088c9e7940e22153993b5c2a2d5bf93b27 288.096915764000 174977 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 99141, "vin": [ { "gen": { "height": 99131 } } ], "vout": [ { "amount": 288096915764, "target": { "key": "2e12c22c120d256627725daeb3899e088c9e7940e22153993b5c2a2d5bf93b27" } } ], "extra": [ 1, 10, 51, 8, 219, 74, 253, 128, 53, 176, 231, 96, 177, 1, 145, 173, 27, 6, 126, 52, 43, 102, 170, 150, 205, 117, 45, 170, 31, 30, 170, 85, 52, 2, 17, 0, 0, 0, 2, 57, 190, 53, 251, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8