Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c42ad738c1691941c5b7a40d559da05aecf1cf132db17f1bd1a84d37d69f0937

Tx prefix hash: 82d0ecdf0e01ae54896bb09cdbbf732ebc20193ab05dffc347dc631875993418
Tx public key: 772ab4807856e1d345475779fb06e9b4cefcf0b3045dd98e69568f654df3ff0d
Timestamp: 1649486568 Timestamp [UCT]: 2022-04-09 06:42:48 Age [y:d:h:m:s]: 03:047:03:44:47
Block: 476378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 814180 RingCT/type: yes/0
Extra: 01772ab4807856e1d345475779fb06e9b4cefcf0b3045dd98e69568f654df3ff0d021100000008a8c141c5000000000000000000

1 output(s) for total of 16.201759165000 dcy

stealth address amount amount idx
00: 9baf04e2c2b88ed4ae1caa20bf897721e8f1104387456aa12df399cddefdcd8c 16.201759165000 896833 of 0

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": 476388, "vin": [ { "gen": { "height": 476378 } } ], "vout": [ { "amount": 16201759165, "target": { "key": "9baf04e2c2b88ed4ae1caa20bf897721e8f1104387456aa12df399cddefdcd8c" } } ], "extra": [ 1, 119, 42, 180, 128, 120, 86, 225, 211, 69, 71, 87, 121, 251, 6, 233, 180, 206, 252, 240, 179, 4, 93, 217, 142, 105, 86, 143, 101, 77, 243, 255, 13, 2, 17, 0, 0, 0, 8, 168, 193, 65, 197, 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