Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55a1d9f85a14c7dcfb2943c29d644f550fc39328ae034f05c2a5236da42c38ce

Tx prefix hash: 201b533421c9612ab2ff4654050e3811007561ede65dade0c78614ce1b6c8911
Tx public key: e9a042377cb625853bf41a184f086061f213384d3a7d2df83a85e0ac1b43b508
Timestamp: 1702644234 Timestamp [UCT]: 2023-12-15 12:43:54 Age [y:d:h:m:s]: 01:328:14:53:58
Block: 913660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493722 RingCT/type: yes/0
Extra: 01e9a042377cb625853bf41a184f086061f213384d3a7d2df83a85e0ac1b43b508021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 500d5b3bdf02800fb2242413272af12149a96ab178e6aed92f961c5fb1ebbdbe 0.600000000000 1370936 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": 913670, "vin": [ { "gen": { "height": 913660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "500d5b3bdf02800fb2242413272af12149a96ab178e6aed92f961c5fb1ebbdbe" } } ], "extra": [ 1, 233, 160, 66, 55, 124, 182, 37, 133, 59, 244, 26, 24, 79, 8, 96, 97, 242, 19, 56, 77, 58, 125, 45, 248, 58, 133, 224, 172, 27, 67, 181, 8, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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