Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f21c2bb914f03bbe81f717518f9f97ca870ba715db2a9c540e289ccc6601f24

Tx prefix hash: ba955541e1e45f2e8839c4c000e345c080271f6cdbd2e243ff91a9081bd9a47e
Tx public key: b9ca11e42c6afdffce9b64c17c13709fcb11d4e3ca332b66110b7ef7773d86e2
Timestamp: 1720475714 Timestamp [UCT]: 2024-07-08 21:55:14 Age [y:d:h:m:s]: 00:272:03:43:03
Block: 1061511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194423 RingCT/type: yes/0
Extra: 01b9ca11e42c6afdffce9b64c17c13709fcb11d4e3ca332b66110b7ef7773d86e202110000000ec26d3a99000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 709ba6fec9c0a36cb50e90cf315fe2c8f1ee9461a25346d30df7834480e893e5 0.600000000000 1532002 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": 1061521, "vin": [ { "gen": { "height": 1061511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "709ba6fec9c0a36cb50e90cf315fe2c8f1ee9461a25346d30df7834480e893e5" } } ], "extra": [ 1, 185, 202, 17, 228, 44, 106, 253, 255, 206, 155, 100, 193, 124, 19, 112, 159, 203, 17, 212, 227, 202, 51, 43, 102, 17, 11, 126, 247, 119, 61, 134, 226, 2, 17, 0, 0, 0, 14, 194, 109, 58, 153, 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