Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edce9757b919514aadd95bd320fbaa01de0777f6ddf0a8e730708a775edb38fd

Tx prefix hash: e36019342c715533bd27d0fdf773275941bdfed00ff128d2ab5082ccc6a1c31c
Tx public key: 6846ea30370bb5705673b35414f9ffed7f1847c9c15d0b0acdeff4dfe9f93d0f
Timestamp: 1592924807 Timestamp [UCT]: 2020-06-23 15:06:47 Age [y:d:h:m:s]: 04:146:14:47:55
Block: 110350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1044416 RingCT/type: yes/0
Extra: 016846ea30370bb5705673b35414f9ffed7f1847c9c15d0b0acdeff4dfe9f93d0f0211000000748a2ee0d9000000000000000000

1 output(s) for total of 264.481565544000 dcy

stealth address amount amount idx
00: 27814a456867e9463b1e01b47d92c96e2ee5cee51be9f2f130bedbc66a43eac6 264.481565544000 191134 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": 110360, "vin": [ { "gen": { "height": 110350 } } ], "vout": [ { "amount": 264481565544, "target": { "key": "27814a456867e9463b1e01b47d92c96e2ee5cee51be9f2f130bedbc66a43eac6" } } ], "extra": [ 1, 104, 70, 234, 48, 55, 11, 181, 112, 86, 115, 179, 84, 20, 249, 255, 237, 127, 24, 71, 201, 193, 93, 11, 10, 205, 239, 244, 223, 233, 249, 61, 15, 2, 17, 0, 0, 0, 116, 138, 46, 224, 217, 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