Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ef04d3b1bfadf210a09514ddb75ec8abd817d6e9668450d9bded8dc53cb811

Tx prefix hash: 57d3500a721b83292a300bb834e70317eec07ad1fa31c9dbc1d8774ce1bf110c
Tx public key: a22c5b011cd47328c828c645796fc7aa97e59dae73662dc2f6fdad331c505816
Timestamp: 1718087535 Timestamp [UCT]: 2024-06-11 06:32:15 Age [y:d:h:m:s]: 00:284:15:02:47
Block: 1041706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203400 RingCT/type: yes/0
Extra: 01a22c5b011cd47328c828c645796fc7aa97e59dae73662dc2f6fdad331c5058160211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa5fdf51cf6d662d0dd736907a8c3a645184af2c44f1af17d92b487465a4e6b3 0.600000000000 1510447 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": 1041716, "vin": [ { "gen": { "height": 1041706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa5fdf51cf6d662d0dd736907a8c3a645184af2c44f1af17d92b487465a4e6b3" } } ], "extra": [ 1, 162, 44, 91, 1, 28, 212, 115, 40, 200, 40, 198, 69, 121, 111, 199, 170, 151, 229, 157, 174, 115, 102, 45, 194, 246, 253, 173, 51, 28, 80, 88, 22, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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