Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37d2bf6900ff231535eb5410ac74f099e0b39762d1d9dad17e17528a905d0f48

Tx prefix hash: 43ebe56b35a3d92c8f8af3d2d063fc3a32076b3d11dc1246d306e76fff3ee3b9
Tx public key: f17f246fc87ff4fe1c1faed6cfc76fbc3df1e1c3f7f662299496819401e65d35
Timestamp: 1740542914 Timestamp [UCT]: 2025-02-26 04:08:34 Age [y:d:h:m:s]: 00:256:14:46:12
Block: 1227403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181152 RingCT/type: yes/0
Extra: 01f17f246fc87ff4fe1c1faed6cfc76fbc3df1e1c3f7f662299496819401e65d350211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51eed178a78f4225e250af270ddbf7c26523e94317afa1a540ad9855cdf95a1a 0.600000000000 1714276 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": 1227413, "vin": [ { "gen": { "height": 1227403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51eed178a78f4225e250af270ddbf7c26523e94317afa1a540ad9855cdf95a1a" } } ], "extra": [ 1, 241, 127, 36, 111, 200, 127, 244, 254, 28, 31, 174, 214, 207, 199, 111, 188, 61, 241, 225, 195, 247, 246, 98, 41, 148, 150, 129, 148, 1, 230, 93, 53, 2, 17, 0, 0, 0, 2, 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