Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ed332cb11ca185620acf2d1c779ffb47ad815eda0ce8f504c2759de0fd1113

Tx prefix hash: bf1e394d519c8c3e98ae6125af3e92542e44e613c04274c15dd78cf5f34ecca8
Tx public key: 6ce53d2101caab33789f4bd80fdf87c070f6cccc453fd9d75bc341ed765f3a13
Timestamp: 1709682577 Timestamp [UCT]: 2024-03-05 23:49:37 Age [y:d:h:m:s]: 01:043:10:13:11
Block: 972027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292042 RingCT/type: yes/0
Extra: 016ce53d2101caab33789f4bd80fdf87c070f6cccc453fd9d75bc341ed765f3a130211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74c06afb74772d69ce0b763f6fed1b221aa122031c1a3b0caa045128c4c8a11c 0.600000000000 1431932 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": 972037, "vin": [ { "gen": { "height": 972027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74c06afb74772d69ce0b763f6fed1b221aa122031c1a3b0caa045128c4c8a11c" } } ], "extra": [ 1, 108, 229, 61, 33, 1, 202, 171, 51, 120, 159, 75, 216, 15, 223, 135, 192, 112, 246, 204, 204, 69, 63, 217, 215, 91, 195, 65, 237, 118, 95, 58, 19, 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