Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf53402aefe5b0552981d646b563b62848c1e54191730b58d77fa5eddd0525c

Tx prefix hash: cdcd4e6bc055f992ae82c6bb2569991de9cc7dca407b5a896aa4d87427096dc5
Tx public key: 5ca0e1729d6f8253769cbdec3d16cbf597009ceda6a57ca3c4a62a1c05fb1ac2
Timestamp: 1736901246 Timestamp [UCT]: 2025-01-15 00:34:06 Age [y:d:h:m:s]: 00:153:16:15:09
Block: 1197526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109546 RingCT/type: yes/0
Extra: 015ca0e1729d6f8253769cbdec3d16cbf597009ceda6a57ca3c4a62a1c05fb1ac2021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1a27996cf94a562c98ea13185f204171cd6bb99188be5e0a018283f89e2a0c0 0.600000000000 1684137 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": 1197536, "vin": [ { "gen": { "height": 1197526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1a27996cf94a562c98ea13185f204171cd6bb99188be5e0a018283f89e2a0c0" } } ], "extra": [ 1, 92, 160, 225, 114, 157, 111, 130, 83, 118, 156, 189, 236, 61, 22, 203, 245, 151, 0, 156, 237, 166, 165, 124, 163, 196, 166, 42, 28, 5, 251, 26, 194, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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