Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 255d0e9ebbe20ae3611aca1df13738c428de4732a7e3140c41099fc559ca98b0

Tx prefix hash: 9e0927c2eb8d602fae4ad9f9c7709818a31bd548302d05f5ee72c3baae16bb62
Tx public key: f859479b21d5353c10f343504e2b837e1dd66d67b9ffca0d32b2528001e0d2fb
Timestamp: 1725237847 Timestamp [UCT]: 2024-09-02 00:44:07 Age [y:d:h:m:s]: 00:225:05:22:49
Block: 1100987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160818 RingCT/type: yes/0
Extra: 01f859479b21d5353c10f343504e2b837e1dd66d67b9ffca0d32b2528001e0d2fb021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be48ec558ac16ae65f85e827b4fb30957337ae3a1a130a45bedb2f1e1eca03b7 0.600000000000 1576968 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": 1100997, "vin": [ { "gen": { "height": 1100987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be48ec558ac16ae65f85e827b4fb30957337ae3a1a130a45bedb2f1e1eca03b7" } } ], "extra": [ 1, 248, 89, 71, 155, 33, 213, 53, 60, 16, 243, 67, 80, 78, 43, 131, 126, 29, 214, 109, 103, 185, 255, 202, 13, 50, 178, 82, 128, 1, 224, 210, 251, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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