Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258c8ef81284d545443633723bf277b8748225d85c9a19d666fdf9482aac1f80

Tx prefix hash: 884841b4c3cf7625a549df615f8b6019766e8fed48127262dd8a1149ef300748
Tx public key: cc36817c2137821fab8daa0788e169c7e81b5fb529959a583f9d3c9f3a94a8d6
Timestamp: 1743323059 Timestamp [UCT]: 2025-03-30 08:24:19 Age [y:d:h:m:s]: 00:308:03:55:37
Block: 1250419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217898 RingCT/type: yes/0
Extra: 01cc36817c2137821fab8daa0788e169c7e81b5fb529959a583f9d3c9f3a94a8d60211000000011a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d140809a904bb6aba5e72d13d14437a950b01156cf2b5ae41689529494ea5d1 0.600000000000 1737468 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": 1250429, "vin": [ { "gen": { "height": 1250419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d140809a904bb6aba5e72d13d14437a950b01156cf2b5ae41689529494ea5d1" } } ], "extra": [ 1, 204, 54, 129, 124, 33, 55, 130, 31, 171, 141, 170, 7, 136, 225, 105, 199, 232, 27, 95, 181, 41, 149, 154, 88, 63, 157, 60, 159, 58, 148, 168, 214, 2, 17, 0, 0, 0, 1, 26, 151, 4, 3, 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