Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d88a42e4750a40d5f29e19a1adfb88526c2f2074f5d1e02a2a4f347313497f03

Tx prefix hash: bd3ce11cd4502514e9bc1dd9e1f727c08711647b025a334d34eba84adffdad1c
Tx public key: feed07bbf806e47a56621288f0c753be1581d784c7acbd8bba6e1cd562b55ab9
Timestamp: 1736715111 Timestamp [UCT]: 2025-01-12 20:51:51 Age [y:d:h:m:s]: 00:076:00:40:51
Block: 1195984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54125 RingCT/type: yes/0
Extra: 01feed07bbf806e47a56621288f0c753be1581d784c7acbd8bba6e1cd562b55ab90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f8aa3645782b03ef3efc4b364542a5b5d6ce7814d0a6a01dd4de61d58617e53 0.600000000000 1682581 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": 1195994, "vin": [ { "gen": { "height": 1195984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f8aa3645782b03ef3efc4b364542a5b5d6ce7814d0a6a01dd4de61d58617e53" } } ], "extra": [ 1, 254, 237, 7, 187, 248, 6, 228, 122, 86, 98, 18, 136, 240, 199, 83, 190, 21, 129, 215, 132, 199, 172, 189, 139, 186, 110, 28, 213, 98, 181, 90, 185, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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