Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9705e02f27421fd58c8a94990b98ebc6894452aa456cea69946551ebadb9b6f9

Tx prefix hash: 5e97e7435ef86f1bb72fef4b324322fabb9d0f8745d202f816998536c35ed7b0
Tx public key: 14dbbc0da50ad6a3372e0f26dfe8e192157f7b56f7e72222066140f4ae76ac4e
Timestamp: 1704616786 Timestamp [UCT]: 2024-01-07 08:39:46 Age [y:d:h:m:s]: 01:161:04:19:32
Block: 930007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376244 RingCT/type: yes/0
Extra: 0114dbbc0da50ad6a3372e0f26dfe8e192157f7b56f7e72222066140f4ae76ac4e02110000001452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7815c3bfb6ae595d08752fd8fd6985fec85ff75d3288ed62d76ca7a1467f3c5 0.600000000000 1387885 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": 930017, "vin": [ { "gen": { "height": 930007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7815c3bfb6ae595d08752fd8fd6985fec85ff75d3288ed62d76ca7a1467f3c5" } } ], "extra": [ 1, 20, 219, 188, 13, 165, 10, 214, 163, 55, 46, 15, 38, 223, 232, 225, 146, 21, 127, 123, 86, 247, 231, 34, 34, 6, 97, 64, 244, 174, 118, 172, 78, 2, 17, 0, 0, 0, 20, 82, 212, 126, 148, 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