Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef82de23f7aabe997fe0a5a957992accf4c21fb566b12c963bfb710c067569ba

Tx prefix hash: 55a63b8c34351e7eaa6b4568903d1ff9f824261d100d68ae617068f9436251c9
Tx public key: 0ae83ab74b661b359309b8f157c4ea50440a057c1f3e2ec9bd685c0e4c3dfacc
Timestamp: 1706540330 Timestamp [UCT]: 2024-01-29 14:58:50 Age [y:d:h:m:s]: 01:065:11:05:44
Block: 945947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307858 RingCT/type: yes/0
Extra: 010ae83ab74b661b359309b8f157c4ea50440a057c1f3e2ec9bd685c0e4c3dfacc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60af8f284b039efa015890d453676169066c773505e1937872757ea10b71b2ce 0.600000000000 1404277 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": 945957, "vin": [ { "gen": { "height": 945947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60af8f284b039efa015890d453676169066c773505e1937872757ea10b71b2ce" } } ], "extra": [ 1, 10, 232, 58, 183, 75, 102, 27, 53, 147, 9, 184, 241, 87, 196, 234, 80, 68, 10, 5, 124, 31, 62, 46, 201, 189, 104, 92, 14, 76, 61, 250, 204, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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