Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65a67e404e5638aa14f0676215c8dac9094daf995cbd43004dc51be793ab0b69

Tx prefix hash: e0f4df65c86626274b34bb8c1dfc5452169146fc27cd91f43c8d672fbf9121a4
Tx public key: fe5039a3033573c263fa6791d74cff27c74aa8dedbab5d0e3c48bfb76fe757d3
Timestamp: 1589363619 Timestamp [UCT]: 2020-05-13 09:53:39 Age [y:d:h:m:s]: 04:264:13:03:05
Block: 100487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108886 RingCT/type: yes/0
Extra: 01fe5039a3033573c263fa6791d74cff27c74aa8dedbab5d0e3c48bfb76fe757d30211000002956fa03929000000000000000000

1 output(s) for total of 285.131773950000 dcy

stealth address amount amount idx
00: df4705949937320db2eef9a51a5a8bdafbdc4f25b9568a056961e2791452d8b1 285.131773950000 177031 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": 100497, "vin": [ { "gen": { "height": 100487 } } ], "vout": [ { "amount": 285131773950, "target": { "key": "df4705949937320db2eef9a51a5a8bdafbdc4f25b9568a056961e2791452d8b1" } } ], "extra": [ 1, 254, 80, 57, 163, 3, 53, 115, 194, 99, 250, 103, 145, 215, 76, 255, 39, 199, 74, 168, 222, 219, 171, 93, 14, 60, 72, 191, 183, 111, 231, 87, 211, 2, 17, 0, 0, 2, 149, 111, 160, 57, 41, 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