Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99aaeaef5429e4ff80a893d0614873ce20bb4a94b8e23cf591c8bb35e9a97c1e

Tx prefix hash: 8c13a3140bceb9f44f55108729d7ab50ae8abce356f547597664587f9364bcaf
Tx public key: 01f8b6595fabb43af6b9d37e0016337ff3f7efbf6e50f02998b5e201ecf027af
Timestamp: 1736753016 Timestamp [UCT]: 2025-01-13 07:23:36 Age [y:d:h:m:s]: 00:064:02:38:30
Block: 1196305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45603 RingCT/type: yes/0
Extra: 0101f8b6595fabb43af6b9d37e0016337ff3f7efbf6e50f02998b5e201ecf027af0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 791ed389615245c38e1d726b9f7da0fc1fe2c7ce4b432e811b30d78147408e4e 0.600000000000 1682904 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": 1196315, "vin": [ { "gen": { "height": 1196305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "791ed389615245c38e1d726b9f7da0fc1fe2c7ce4b432e811b30d78147408e4e" } } ], "extra": [ 1, 1, 248, 182, 89, 95, 171, 180, 58, 246, 185, 211, 126, 0, 22, 51, 127, 243, 247, 239, 191, 110, 80, 240, 41, 152, 181, 226, 1, 236, 240, 39, 175, 2, 17, 0, 0, 0, 1, 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