Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 571fdf3022d80dcaaedbe4ade1b8647f236c34eaab98e2dc8b2e09ec20939398

Tx prefix hash: 2dc85149eb85f5d36bc60293b14e23695ce41854e0dc804e13c6b4df2c2faaa4
Tx public key: 14e5c76790af5cf84a21659b0f9acad58b92969dd2fb8337a074424c065423ee
Timestamp: 1685837016 Timestamp [UCT]: 2023-06-04 00:03:36 Age [y:d:h:m:s]: 01:269:09:00:21
Block: 774568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453697 RingCT/type: yes/0
Extra: 0114e5c76790af5cf84a21659b0f9acad58b92969dd2fb8337a074424c065423ee0211000000024b8f5122000000000000000000

1 output(s) for total of 1.665462447000 dcy

stealth address amount amount idx
00: 4351d510d6ababd27d76cf6dcffa7a0117e9dff86268b8c8a26320527e5d55ef 1.665462447000 1224051 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": 774578, "vin": [ { "gen": { "height": 774568 } } ], "vout": [ { "amount": 1665462447, "target": { "key": "4351d510d6ababd27d76cf6dcffa7a0117e9dff86268b8c8a26320527e5d55ef" } } ], "extra": [ 1, 20, 229, 199, 103, 144, 175, 92, 248, 74, 33, 101, 155, 15, 154, 202, 213, 139, 146, 150, 157, 210, 251, 131, 55, 160, 116, 66, 76, 6, 84, 35, 238, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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