Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8a034cba766070c642735c4a410f39b62c2502d2a30b839a65a6f56ff4000f3

Tx prefix hash: 44c6e49ee6cad0d22d2e4817c91291c3f4f97ecafaff562a7877b9cb80a6211b
Tx public key: ed13e8f82be2b8157dc1b151bb97b3a8c35a99ec0f55eeb547b495cd89cdf9d8
Timestamp: 1706694272 Timestamp [UCT]: 2024-01-31 09:44:32 Age [y:d:h:m:s]: 01:282:05:01:50
Block: 947227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460489 RingCT/type: yes/0
Extra: 01ed13e8f82be2b8157dc1b151bb97b3a8c35a99ec0f55eeb547b495cd89cdf9d80211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5f1c3d48052d5d95811410bd6acf91792383129425bdf704419060c0dd2e225 0.600000000000 1405575 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": 947237, "vin": [ { "gen": { "height": 947227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5f1c3d48052d5d95811410bd6acf91792383129425bdf704419060c0dd2e225" } } ], "extra": [ 1, 237, 19, 232, 248, 43, 226, 184, 21, 125, 193, 177, 81, 187, 151, 179, 168, 195, 90, 153, 236, 15, 85, 238, 181, 71, 180, 149, 205, 137, 205, 249, 216, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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