Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d23147bf76c17d6c8bb5b99e85a22cd6edcb82f823c801ec37e61e336716b09f

Tx prefix hash: 865dd78ddec6545bd9294fe74fcfbc5f1ca8067a6c730bdb4e22bed90d5addd4
Tx public key: 3ece6b3c8045b6562d2164b8ce61a12cee2734d8401d5cabbd69046d6ef5d708
Timestamp: 1706311724 Timestamp [UCT]: 2024-01-26 23:28:44 Age [y:d:h:m:s]: 00:292:10:20:44
Block: 944038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209407 RingCT/type: yes/0
Extra: 013ece6b3c8045b6562d2164b8ce61a12cee2734d8401d5cabbd69046d6ef5d70802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4edf5e2d2093d63d8e432727000a620a4f99c50e54001ed5d47799109e25e4e3 0.600000000000 1402264 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": 944048, "vin": [ { "gen": { "height": 944038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4edf5e2d2093d63d8e432727000a620a4f99c50e54001ed5d47799109e25e4e3" } } ], "extra": [ 1, 62, 206, 107, 60, 128, 69, 182, 86, 45, 33, 100, 184, 206, 97, 161, 44, 238, 39, 52, 216, 64, 29, 92, 171, 189, 105, 4, 109, 110, 245, 215, 8, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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