Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2109c5349a16bcda28ba4d3ded77032b4e6f55c24e647759c6c8e348286a51

Tx prefix hash: 5fef5c901750756039d55786ab5a74f600df7890a14c3f80d4edba2936b0c8e2
Tx public key: d30afe9f54f695a0ec7b27fcedde51aba9e9147c226192e1e0e691239b42147d
Timestamp: 1731791255 Timestamp [UCT]: 2024-11-16 21:07:35 Age [y:d:h:m:s]: 00:174:00:57:53
Block: 1155207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124236 RingCT/type: yes/0
Extra: 01d30afe9f54f695a0ec7b27fcedde51aba9e9147c226192e1e0e691239b42147d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 619c76b85c2c4621f891a65c0e371e15267d4acfdbebac6386e8ee48c5ca4da6 0.600000000000 1640822 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": 1155217, "vin": [ { "gen": { "height": 1155207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "619c76b85c2c4621f891a65c0e371e15267d4acfdbebac6386e8ee48c5ca4da6" } } ], "extra": [ 1, 211, 10, 254, 159, 84, 246, 149, 160, 236, 123, 39, 252, 237, 222, 81, 171, 169, 233, 20, 124, 34, 97, 146, 225, 224, 230, 145, 35, 155, 66, 20, 125, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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