Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17e56cce99c61e5a56d3ae12e161f80ef422ea241d140374b412a28c17027d9

Tx prefix hash: 17ab6ec0b8d5512a1e884df54a283f07e40bd825c8cf2a048a79d40523486e84
Tx public key: c1b1f30b29a3c6d9a7ecdcf5107b2645ecbbd99316ff80d633b97f96495eede3
Timestamp: 1732612062 Timestamp [UCT]: 2024-11-26 09:07:42 Age [y:d:h:m:s]: 00:118:14:50:24
Block: 1162015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84574 RingCT/type: yes/0
Extra: 01c1b1f30b29a3c6d9a7ecdcf5107b2645ecbbd99316ff80d633b97f96495eede3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de29f116ee40a48493ed6d25eb2d92deb2c03a06489e0f2c6ceeead12f058293 0.600000000000 1647670 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": 1162025, "vin": [ { "gen": { "height": 1162015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de29f116ee40a48493ed6d25eb2d92deb2c03a06489e0f2c6ceeead12f058293" } } ], "extra": [ 1, 193, 177, 243, 11, 41, 163, 198, 217, 167, 236, 220, 245, 16, 123, 38, 69, 236, 187, 217, 147, 22, 255, 128, 214, 51, 185, 127, 150, 73, 94, 237, 227, 2, 17, 0, 0, 0, 3, 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