Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a296af07b8a3d0b4e6b8a74165868af0ccec636b62edaf4c1f7031b69f0c18d

Tx prefix hash: 4d5dc0516ce61f5c6a3d937825b3be85362479b5f0042b33394734c7b40f1963
Tx public key: 60907a1ec53798d9a9dbb323bfeebd14d988ee067d9d9af266ca2289e3f106cb
Timestamp: 1576424829 Timestamp [UCT]: 2019-12-15 15:47:09 Age [y:d:h:m:s]: 05:050:00:55:57
Block: 27510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182387 RingCT/type: yes/0
Extra: 0160907a1ec53798d9a9dbb323bfeebd14d988ee067d9d9af266ca2289e3f106cb021100000003ad433a0b000000000000000000

1 output(s) for total of 497.563845861000 dcy

stealth address amount amount idx
00: be2c9850a4b88aa3f4a84ea35c3c6f9cd79a75586c29d9830f2d7d05dec7072e 497.563845861000 45516 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": 27520, "vin": [ { "gen": { "height": 27510 } } ], "vout": [ { "amount": 497563845861, "target": { "key": "be2c9850a4b88aa3f4a84ea35c3c6f9cd79a75586c29d9830f2d7d05dec7072e" } } ], "extra": [ 1, 96, 144, 122, 30, 197, 55, 152, 217, 169, 219, 179, 35, 191, 238, 189, 20, 217, 136, 238, 6, 125, 157, 154, 242, 102, 202, 34, 137, 227, 241, 6, 203, 2, 17, 0, 0, 0, 3, 173, 67, 58, 11, 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