Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6917de8c0b52a57db899bb6a4ab81eff8afda795a58677fd4ac912a4f4463ed8

Tx prefix hash: 3c11a88329c564aa14654e69a4d3024f129f4ac40fd2498d60fda61e1a404a7c
Tx public key: 417cb89cd3dbfe5e2815160fa4a4dd7c92c818bc687d61388787d3ca80eac522
Timestamp: 1733105103 Timestamp [UCT]: 2024-12-02 02:05:03 Age [y:d:h:m:s]: 00:107:17:48:43
Block: 1166104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76820 RingCT/type: yes/0
Extra: 01417cb89cd3dbfe5e2815160fa4a4dd7c92c818bc687d61388787d3ca80eac522021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00c4736f1c05e0efaae95c2f2a01d1279c4fb7a06d9b4b1e8d236d574001bdcf 0.600000000000 1651781 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": 1166114, "vin": [ { "gen": { "height": 1166104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00c4736f1c05e0efaae95c2f2a01d1279c4fb7a06d9b4b1e8d236d574001bdcf" } } ], "extra": [ 1, 65, 124, 184, 156, 211, 219, 254, 94, 40, 21, 22, 15, 164, 164, 221, 124, 146, 200, 24, 188, 104, 125, 97, 56, 135, 135, 211, 202, 128, 234, 197, 34, 2, 17, 0, 0, 0, 4, 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