Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a834e785e41101adc4a95f2aa72b7657a9d60fc1a1f427bcbfc1a29fa4839866

Tx prefix hash: 1de6aee3f194ff974761aae46cc1e56d09b2c63af4761312b517e031b1472086
Tx public key: d310f82db2ccfad80971a86500e6a212ee1989155d09bdb0e41ff7b28d57e8a1
Timestamp: 1711179353 Timestamp [UCT]: 2024-03-23 07:35:53 Age [y:d:h:m:s]: 01:243:17:09:53
Block: 984454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432858 RingCT/type: yes/0
Extra: 01d310f82db2ccfad80971a86500e6a212ee1989155d09bdb0e41ff7b28d57e8a10211000000010424019c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e95e4f3f0824770b00e19373b1b60c3aa2ff52e60a3f801a025941b722b7ee9a 0.600000000000 1444625 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": 984464, "vin": [ { "gen": { "height": 984454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e95e4f3f0824770b00e19373b1b60c3aa2ff52e60a3f801a025941b722b7ee9a" } } ], "extra": [ 1, 211, 16, 248, 45, 178, 204, 250, 216, 9, 113, 168, 101, 0, 230, 162, 18, 238, 25, 137, 21, 93, 9, 189, 176, 228, 31, 247, 178, 141, 87, 232, 161, 2, 17, 0, 0, 0, 1, 4, 36, 1, 156, 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