Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a169735669b903d8fa62611ede050015b8993a3fc901321bfa9ac7ad7781a7b

Tx prefix hash: 72fe0443483ad832c753726bcdccb20a0fb74ec7e44f6ccbe726ca20883c7de9
Tx public key: 6a2e72a2e8fdd4aa32770bbafa9cc28e4a5c0318596c2913406269ec6183ac75
Timestamp: 1588735400 Timestamp [UCT]: 2020-05-06 03:23:20 Age [y:d:h:m:s]: 04:036:08:35:57
Block: 98834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 942317 RingCT/type: yes/0
Extra: 016a2e72a2e8fdd4aa32770bbafa9cc28e4a5c0318596c2913406269ec6183ac750211000000036fa03929000000000000000000

1 output(s) for total of 288.750465922000 dcy

stealth address amount amount idx
00: 758bdb5ac609c64bd5dc1f702262e3a9b57da0ecd2acf8c94c5c882e13bf6708 288.750465922000 174608 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": 98844, "vin": [ { "gen": { "height": 98834 } } ], "vout": [ { "amount": 288750465922, "target": { "key": "758bdb5ac609c64bd5dc1f702262e3a9b57da0ecd2acf8c94c5c882e13bf6708" } } ], "extra": [ 1, 106, 46, 114, 162, 232, 253, 212, 170, 50, 119, 11, 186, 250, 156, 194, 142, 74, 92, 3, 24, 89, 108, 41, 19, 64, 98, 105, 236, 97, 131, 172, 117, 2, 17, 0, 0, 0, 3, 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