Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16875a94b109896e0f30c52e6630095f0b03624c540af7f296f3e24f185b8bab

Tx prefix hash: 3f29d6be52fc8d3ca5237be70b9d32edea529ac0beb4faf72508d2ecc42613e3
Tx public key: 7fc9796707c3fb00453ba84895a4d5c1c7923b79f48505ff07ee403c5035d6b2
Timestamp: 1665715100 Timestamp [UCT]: 2022-10-14 02:38:20 Age [y:d:h:m:s]: 03:024:04:10:26
Block: 608566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 797464 RingCT/type: yes/0
Extra: 017fc9796707c3fb00453ba84895a4d5c1c7923b79f48505ff07ee403c5035d6b202110000000371bd5189000000000000000000

1 output(s) for total of 5.909738463000 dcy

stealth address amount amount idx
00: 71aef02bfee44b843d01b63d09c880c5f21c4a0caef7d7371db10aebd7d5287e 5.909738463000 1045275 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": 608576, "vin": [ { "gen": { "height": 608566 } } ], "vout": [ { "amount": 5909738463, "target": { "key": "71aef02bfee44b843d01b63d09c880c5f21c4a0caef7d7371db10aebd7d5287e" } } ], "extra": [ 1, 127, 201, 121, 103, 7, 195, 251, 0, 69, 59, 168, 72, 149, 164, 213, 193, 199, 146, 59, 121, 244, 133, 5, 255, 7, 238, 64, 60, 80, 53, 214, 178, 2, 17, 0, 0, 0, 3, 113, 189, 81, 137, 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