Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de8158d1814c915008e6f94a2f7057799fbf2fab7478389ba0e1ab0d91121b4e

Tx prefix hash: 7409277fd8fbae1cf5706c2d801a889418886e5a8889c7321e3e533939bea259
Tx public key: b13d2a79c52c25712a31a6e3bb3d78f5ff7bdcb4698e33f832ce48fc54e519f4
Timestamp: 1739522137 Timestamp [UCT]: 2025-02-14 08:35:37 Age [y:d:h:m:s]: 00:325:15:15:24
Block: 1218967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230567 RingCT/type: yes/0
Extra: 01b13d2a79c52c25712a31a6e3bb3d78f5ff7bdcb4698e33f832ce48fc54e519f40211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e76b5b8b05eee52484874dc0f8ea691198537f8a8e5e65570e5488beb11d72d7 0.600000000000 1705788 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": 1218977, "vin": [ { "gen": { "height": 1218967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e76b5b8b05eee52484874dc0f8ea691198537f8a8e5e65570e5488beb11d72d7" } } ], "extra": [ 1, 177, 61, 42, 121, 197, 44, 37, 113, 42, 49, 166, 227, 187, 61, 120, 245, 255, 123, 220, 180, 105, 142, 51, 248, 50, 206, 72, 252, 84, 229, 25, 244, 2, 17, 0, 0, 0, 4, 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