Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71d5f52508aff77e5f5a2dbcf3af2b4ef5da7001ae6e767ba86595ed547cf7b

Tx prefix hash: ab30d6f747a8d641c7bd19b806dd86474f4a66c076ad2aab861a75af6cc955d3
Tx public key: 290d32f89605463441a8d4c94c9319d1e63fd2185b03d348c50c5fd1b56d558e
Timestamp: 1740136428 Timestamp [UCT]: 2025-02-21 11:13:48 Age [y:d:h:m:s]: 00:340:12:56:33
Block: 1224019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241075 RingCT/type: yes/0
Extra: 01290d32f89605463441a8d4c94c9319d1e63fd2185b03d348c50c5fd1b56d558e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6fe219cb174038088e70b7c479c9638757a2074db5d095bd064a3947d31b991 0.600000000000 1710876 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": 1224029, "vin": [ { "gen": { "height": 1224019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6fe219cb174038088e70b7c479c9638757a2074db5d095bd064a3947d31b991" } } ], "extra": [ 1, 41, 13, 50, 248, 150, 5, 70, 52, 65, 168, 212, 201, 76, 147, 25, 209, 230, 63, 210, 24, 91, 3, 211, 72, 197, 12, 95, 209, 181, 109, 85, 142, 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