Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43eb447cabfd7009b08165a417e71583feaae8a8529f6d41a951e588897e5fe3

Tx prefix hash: a8a90765fd74cf83b224f3f6ca5a89150b8c445765d2472431eaec8d41e7889a
Tx public key: 9121ee46fdb689e86d42805c6b21d665e8eb2ddaa7c06f8bb79625baffa8c8d7
Timestamp: 1682350368 Timestamp [UCT]: 2023-04-24 15:32:48 Age [y:d:h:m:s]: 02:006:04:41:57
Block: 745667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526576 RingCT/type: yes/0
Extra: 019121ee46fdb689e86d42805c6b21d665e8eb2ddaa7c06f8bb79625baffa8c8d7021100000006faf35c9c000000000000000000

1 output(s) for total of 2.076327698000 dcy

stealth address amount amount idx
00: 4d3e76aeed357e26945bc689e36ee0f32754161bca4917f3bbbe8245f7769ea0 2.076327698000 1193138 of 0

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": 745677, "vin": [ { "gen": { "height": 745667 } } ], "vout": [ { "amount": 2076327698, "target": { "key": "4d3e76aeed357e26945bc689e36ee0f32754161bca4917f3bbbe8245f7769ea0" } } ], "extra": [ 1, 145, 33, 238, 70, 253, 182, 137, 232, 109, 66, 128, 92, 107, 33, 214, 101, 232, 235, 45, 218, 167, 192, 111, 139, 183, 150, 37, 186, 255, 168, 200, 215, 2, 17, 0, 0, 0, 6, 250, 243, 92, 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