Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 513dc98abdb5e8ff6d02308055d5d1e3accb2d7caace90f207b6f292a07db573

Tx prefix hash: afdc4bf4423cc420f3f8ca62b35c8df8032aa796ee43f5c721d75abe275c934f
Tx public key: a64fef89385f9ddd3a2be1e7000628b3154ada1d992e0c2b4c59bfe272f19426
Timestamp: 1719748011 Timestamp [UCT]: 2024-06-30 11:46:51 Age [y:d:h:m:s]: 01:132:16:19:15
Block: 1055464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353365 RingCT/type: yes/0
Extra: 01a64fef89385f9ddd3a2be1e7000628b3154ada1d992e0c2b4c59bfe272f194260211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 533f2f74a01893187a6e95e43b8bbfc4a2a2abeebbdd93e051e602aa0db75cf5 0.600000000000 1525865 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": 1055474, "vin": [ { "gen": { "height": 1055464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "533f2f74a01893187a6e95e43b8bbfc4a2a2abeebbdd93e051e602aa0db75cf5" } } ], "extra": [ 1, 166, 79, 239, 137, 56, 95, 157, 221, 58, 43, 225, 231, 0, 6, 40, 179, 21, 74, 218, 29, 153, 46, 12, 43, 76, 89, 191, 226, 114, 241, 148, 38, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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