Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6062ad356f581561b7752bd59553f518db501deaa21361e057f2b33fc5179fc7

Tx prefix hash: 0ad88a20779f91433fef5d09a81c2c2e780f55891e15e983b38587819b7b17f0
Tx public key: a4b6ae603495f44d74b55528a9d4afeb721312f88e280cc0a8af657d02f6a249
Timestamp: 1702656630 Timestamp [UCT]: 2023-12-15 16:10:30 Age [y:d:h:m:s]: 01:032:01:52:49
Block: 913767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284278 RingCT/type: yes/0
Extra: 01a4b6ae603495f44d74b55528a9d4afeb721312f88e280cc0a8af657d02f6a24902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a59303b615310e65a2db0f053c01af8e0ef23773e3e0b1e97917c8eead958a53 0.600000000000 1371045 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": 913777, "vin": [ { "gen": { "height": 913767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a59303b615310e65a2db0f053c01af8e0ef23773e3e0b1e97917c8eead958a53" } } ], "extra": [ 1, 164, 182, 174, 96, 52, 149, 244, 77, 116, 181, 85, 40, 169, 212, 175, 235, 114, 19, 18, 248, 142, 40, 12, 192, 168, 175, 101, 125, 2, 246, 162, 73, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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