Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d7a4d0af92850aedce145bde807aeeabb4909451d067d4659a40ebddc4aa58

Tx prefix hash: 248551f46706d5ca2e5fb5b392c7c5c3741eebcd00d01feb13d9b67cb8833e27
Tx public key: 6efe6c9d914f03545f08d4a33cdd3e0bd5e54a4866cbe8a4967b3e23a0d89a3a
Timestamp: 1731670102 Timestamp [UCT]: 2024-11-15 11:28:22 Age [y:d:h:m:s]: 00:215:12:21:40
Block: 1154213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153763 RingCT/type: yes/0
Extra: 016efe6c9d914f03545f08d4a33cdd3e0bd5e54a4866cbe8a4967b3e23a0d89a3a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f50f6090539bdc0d2a222266542c093771025d4babc44555e19e52936de04a7d 0.600000000000 1639824 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": 1154223, "vin": [ { "gen": { "height": 1154213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f50f6090539bdc0d2a222266542c093771025d4babc44555e19e52936de04a7d" } } ], "extra": [ 1, 110, 254, 108, 157, 145, 79, 3, 84, 95, 8, 212, 163, 60, 221, 62, 11, 213, 229, 74, 72, 102, 203, 232, 164, 150, 123, 62, 35, 160, 216, 154, 58, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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