Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb9fbb58fddce9738632e0a5d7d8a4a96c90ad370f9ea3be4a73fb63358df8b6

Tx prefix hash: 7b60d3992d512168a17bab3ca16e539ca19036b1bd6c8044702c9d8b3a365e6c
Tx public key: 0047bb97efdaebf651d9d11ef7d4fd91296af2f12d492fc8a2a13d0b603931e4
Timestamp: 1737854718 Timestamp [UCT]: 2025-01-26 01:25:18 Age [y:d:h:m:s]: 00:324:10:21:23
Block: 1205381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229456 RingCT/type: yes/0
Extra: 010047bb97efdaebf651d9d11ef7d4fd91296af2f12d492fc8a2a13d0b603931e4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d4ee5e6b9040f163e1a817e418912161ab672fff4f596740ba717d464db919f 0.600000000000 1692078 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": 1205391, "vin": [ { "gen": { "height": 1205381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d4ee5e6b9040f163e1a817e418912161ab672fff4f596740ba717d464db919f" } } ], "extra": [ 1, 0, 71, 187, 151, 239, 218, 235, 246, 81, 217, 209, 30, 247, 212, 253, 145, 41, 106, 242, 241, 45, 73, 47, 200, 162, 161, 61, 11, 96, 57, 49, 228, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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