Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477f5fe5f3c21726e61be67ca5896e1a3e16721c9d46acc2751bd4af9a6f6c3b

Tx prefix hash: 9679a4355fc2d8f36cd181f98015819966c3453243ec5c1b03fee61ca4dd0136
Tx public key: c252c1ed568af64064aced0ee3c77e4f8a4ed4eac549352f4fafb217634c732b
Timestamp: 1703290823 Timestamp [UCT]: 2023-12-23 00:20:23 Age [y:d:h:m:s]: 01:324:04:28:23
Block: 919028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490532 RingCT/type: yes/0
Extra: 01c252c1ed568af64064aced0ee3c77e4f8a4ed4eac549352f4fafb217634c732b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 152264f7b48fe9b988946929e001c3e0d9503ea96646fc1fbcc5df1adba74817 0.600000000000 1376692 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": 919038, "vin": [ { "gen": { "height": 919028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "152264f7b48fe9b988946929e001c3e0d9503ea96646fc1fbcc5df1adba74817" } } ], "extra": [ 1, 194, 82, 193, 237, 86, 138, 246, 64, 100, 172, 237, 14, 227, 199, 126, 79, 138, 78, 212, 234, 197, 73, 53, 47, 79, 175, 178, 23, 99, 76, 115, 43, 2, 17, 0, 0, 0, 7, 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