Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ee3533d11d3566dab7adbf1cb14650a0e61b4e95ca31e69575d5f8bafdfd9a4

Tx prefix hash: e43caa17b94c4eea539045b66c447806104d095011c1e7d49f33488af25b0e32
Tx public key: 3ffdb63941714e29a8aee61ab62906f070156708366242a41e2c51768871038a
Timestamp: 1694876099 Timestamp [UCT]: 2023-09-16 14:54:59 Age [y:d:h:m:s]: 01:166:12:31:18
Block: 849453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380067 RingCT/type: yes/0
Extra: 013ffdb63941714e29a8aee61ab62906f070156708366242a41e2c51768871038a021100000009faf35c9c000000000000000000

1 output(s) for total of 0.940610113000 dcy

stealth address amount amount idx
00: 64df986ccd0b959fc8e75a881575ee1296f0d42456a8fb4dc187d2f8187bdf4b 0.940610113000 1303119 of 0

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": 849463, "vin": [ { "gen": { "height": 849453 } } ], "vout": [ { "amount": 940610113, "target": { "key": "64df986ccd0b959fc8e75a881575ee1296f0d42456a8fb4dc187d2f8187bdf4b" } } ], "extra": [ 1, 63, 253, 182, 57, 65, 113, 78, 41, 168, 174, 230, 26, 182, 41, 6, 240, 112, 21, 103, 8, 54, 98, 66, 164, 30, 44, 81, 118, 136, 113, 3, 138, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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