Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 494f82517d0eed2efc320208f70ae4ec7c0b36b32953285bf77cd3a9a8cb11c1

Tx prefix hash: 2ce18eb784cc8adecd7f2aa8d6fa7a4b78034c2a01ea5771399e3fae84ff227b
Tx public key: dabb1a50af267096fadf31f64f9b3f354fdef12e2aa9426ba3571c7e2b40ffcd
Timestamp: 1577396068 Timestamp [UCT]: 2019-12-26 21:34:28 Age [y:d:h:m:s]: 05:003:13:33:26
Block: 32461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152511 RingCT/type: yes/0
Extra: 01dabb1a50af267096fadf31f64f9b3f354fdef12e2aa9426ba3571c7e2b40ffcd02110000000dc3a1a09f000000000000000000

1 output(s) for total of 479.119768767000 dcy

stealth address amount amount idx
00: aeea299af5508b0976f1619e525e09e60c36a9dcbc5bb987ef2a848f686af9e6 479.119768767000 53989 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": 32471, "vin": [ { "gen": { "height": 32461 } } ], "vout": [ { "amount": 479119768767, "target": { "key": "aeea299af5508b0976f1619e525e09e60c36a9dcbc5bb987ef2a848f686af9e6" } } ], "extra": [ 1, 218, 187, 26, 80, 175, 38, 112, 150, 250, 223, 49, 246, 79, 155, 63, 53, 79, 222, 241, 46, 42, 169, 66, 107, 163, 87, 28, 126, 43, 64, 255, 205, 2, 17, 0, 0, 0, 13, 195, 161, 160, 159, 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