Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 613e6070da74f25149bdb7ae4a3259f4d425f54c849b421a1bd7f77d0b61b564

Tx prefix hash: 542d292c13ba33dcca314432ee941191ad449d4af0c2d97ee42d32f32d9a2e81
Tx public key: da80e2f32cb53aa9097ab6bf7f1e9805270a7045406d89fd86e03060c46cd0ee
Timestamp: 1737002329 Timestamp [UCT]: 2025-01-16 04:38:49 Age [y:d:h:m:s]: 00:154:03:57:15
Block: 1198359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109877 RingCT/type: yes/0
Extra: 01da80e2f32cb53aa9097ab6bf7f1e9805270a7045406d89fd86e03060c46cd0ee0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3111d3e122bdf80a0c2e3cb212699f54b49e77858bfd7694d50a24bc5c7bc853 0.600000000000 1684982 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": 1198369, "vin": [ { "gen": { "height": 1198359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3111d3e122bdf80a0c2e3cb212699f54b49e77858bfd7694d50a24bc5c7bc853" } } ], "extra": [ 1, 218, 128, 226, 243, 44, 181, 58, 169, 9, 122, 182, 191, 127, 30, 152, 5, 39, 10, 112, 69, 64, 109, 137, 253, 134, 224, 48, 96, 196, 108, 208, 238, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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