Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de3d2098906d662497835631bebb606d03ca29761625dcc3e280def5d9cad20

Tx prefix hash: 4125519d5e48bc341a0064a3191b13b5da59fc465a872356e04cb0738d1e45e4
Tx public key: 7a56d4f5afdedaa0182b2aa6e5430e270d07440c051957e1c0e0e47003576bdc
Timestamp: 1733024036 Timestamp [UCT]: 2024-12-01 03:33:56 Age [y:d:h:m:s]: 00:123:17:30:34
Block: 1165431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88227 RingCT/type: yes/0
Extra: 017a56d4f5afdedaa0182b2aa6e5430e270d07440c051957e1c0e0e47003576bdc0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c7984946c1e3a44efede0d37fa99a91fc9e9268daa4e28f0f8a6ec5cca14cc6 0.600000000000 1651106 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": 1165441, "vin": [ { "gen": { "height": 1165431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c7984946c1e3a44efede0d37fa99a91fc9e9268daa4e28f0f8a6ec5cca14cc6" } } ], "extra": [ 1, 122, 86, 212, 245, 175, 222, 218, 160, 24, 43, 42, 166, 229, 67, 14, 39, 13, 7, 68, 12, 5, 25, 87, 225, 192, 224, 228, 112, 3, 87, 107, 220, 2, 17, 0, 0, 0, 4, 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