Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5335a16ee2b7a4f1a3741e713b21d13aa27078b39f927c68180439dc96f0d6b5

Tx prefix hash: a70daf733e7764c31ae9e8867da608038b7b6a9736c9495dd5206d69dcc27c83
Tx public key: 2a4d80ba2cf49caba1ad31fa1ec104f9c305f5f858141174ce6471f6a2cc3138
Timestamp: 1705016444 Timestamp [UCT]: 2024-01-11 23:40:44 Age [y:d:h:m:s]: 01:156:02:04:54
Block: 933315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372602 RingCT/type: yes/0
Extra: 012a4d80ba2cf49caba1ad31fa1ec104f9c305f5f858141174ce6471f6a2cc31380211000000157a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b18d2ac1cd1a7844ec5c1963fd16cac008c05f4ecee8c09f99e2016d7a5c827 0.600000000000 1391277 of 15

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": 933325, "vin": [ { "gen": { "height": 933315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b18d2ac1cd1a7844ec5c1963fd16cac008c05f4ecee8c09f99e2016d7a5c827" } } ], "extra": [ 1, 42, 77, 128, 186, 44, 244, 156, 171, 161, 173, 49, 250, 30, 193, 4, 249, 195, 5, 245, 248, 88, 20, 17, 116, 206, 100, 113, 246, 162, 204, 49, 56, 2, 17, 0, 0, 0, 21, 122, 156, 244, 199, 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