Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeab1b6ac78d9b68aa408819bdd44c7ec57fdf985bfbda350dbb1cc3c1a86b21

Tx prefix hash: 46b6f57aa2f85495a0eff74e81e1d8961bf7dd7321b1843c2c977547ad4df5a6
Tx public key: 7c051d171018321c9ab29a2cc7fd71afef823f2fd5a61ce243abb1b5ee114f77
Timestamp: 1713994625 Timestamp [UCT]: 2024-04-24 21:37:05 Age [y:d:h:m:s]: 01:241:14:02:23
Block: 1007770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431352 RingCT/type: yes/0
Extra: 017c051d171018321c9ab29a2cc7fd71afef823f2fd5a61ce243abb1b5ee114f770211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54d698231baa3f218dfb016a0911b5e7871802aaf2166ee7f891eb3973eda613 0.600000000000 1469214 of 15

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": 1007780, "vin": [ { "gen": { "height": 1007770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54d698231baa3f218dfb016a0911b5e7871802aaf2166ee7f891eb3973eda613" } } ], "extra": [ 1, 124, 5, 29, 23, 16, 24, 50, 28, 154, 178, 154, 44, 199, 253, 113, 175, 239, 130, 63, 47, 213, 166, 28, 226, 67, 171, 177, 181, 238, 17, 79, 119, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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