Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7090584536a1c7dac7326c90a0be40ed28d4d1b4d100ad6eee5e3e285ea8656a

Tx prefix hash: d4d1a9408110e20714144f199b63eba101e06ea3508b8e1762a5187fbe835678
Tx public key: e8d3fc08a0c9fbab976a23fe337dfba5de7e18e85616d21887c741a070abaac3
Timestamp: 1737420337 Timestamp [UCT]: 2025-01-21 00:45:37 Age [y:d:h:m:s]: 00:148:17:44:51
Block: 1201790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106034 RingCT/type: yes/0
Extra: 01e8d3fc08a0c9fbab976a23fe337dfba5de7e18e85616d21887c741a070abaac30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25d0c73e8286098b62aa83c6ec9d489be9e8e1ca8a614a082f7ac1bd6927a18f 0.600000000000 1688447 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": 1201800, "vin": [ { "gen": { "height": 1201790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25d0c73e8286098b62aa83c6ec9d489be9e8e1ca8a614a082f7ac1bd6927a18f" } } ], "extra": [ 1, 232, 211, 252, 8, 160, 201, 251, 171, 151, 106, 35, 254, 51, 125, 251, 165, 222, 126, 24, 232, 86, 22, 210, 24, 135, 199, 65, 160, 112, 171, 170, 195, 2, 17, 0, 0, 0, 3, 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