Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832082f96740dbd3f6c5c8ce0ba2e0720b4cada8a80314f735a01a60adbab901

Tx prefix hash: 5a2d0dd0fd8e6650f86d8c57bdbbdc96a28dffce75cf1e6b797796af0df1e8de
Tx public key: 16cf646223e32309a85a36615df00956d96a8307bdd55731fa2b5403efa2ae8c
Timestamp: 1705675077 Timestamp [UCT]: 2024-01-19 14:37:57 Age [y:d:h:m:s]: 01:152:12:11:12
Block: 938758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370015 RingCT/type: yes/0
Extra: 0116cf646223e32309a85a36615df00956d96a8307bdd55731fa2b5403efa2ae8c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cea9a57b0117f10ce0f89ff05e5c862a4ca1ae3e100c834b8a3426d7b90b447b 0.600000000000 1396836 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": 938768, "vin": [ { "gen": { "height": 938758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cea9a57b0117f10ce0f89ff05e5c862a4ca1ae3e100c834b8a3426d7b90b447b" } } ], "extra": [ 1, 22, 207, 100, 98, 35, 227, 35, 9, 168, 90, 54, 97, 93, 240, 9, 86, 217, 106, 131, 7, 189, 213, 87, 49, 250, 43, 84, 3, 239, 162, 174, 140, 2, 17, 0, 0, 0, 2, 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