Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f9b5b062d0c4ebd3756862c4cd81d7c47491279f72e21671e02c69e182352fa

Tx prefix hash: eb69c67ef7b80c1ffe2c1bcb618fb35cddac5bad94abbea93c6452499ca0cba7
Tx public key: 579159331af809d3b23644aec0bf381f50b22db15b54816fe3859aaf8daea085
Timestamp: 1608685646 Timestamp [UCT]: 2020-12-23 01:07:26 Age [y:d:h:m:s]: 03:331:01:34:20
Block: 167430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 988668 RingCT/type: yes/0
Extra: 01579159331af809d3b23644aec0bf381f50b22db15b54816fe3859aaf8daea0850211000001eddf1e48bb000000000000000000

1 output(s) for total of 171.106153700000 dcy

stealth address amount amount idx
00: 81f672bbbf9098c67c224d63cec3e1e1110b3a76001bcb6b4b8e456f994d42c3 171.106153700000 308721 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": 167440, "vin": [ { "gen": { "height": 167430 } } ], "vout": [ { "amount": 171106153700, "target": { "key": "81f672bbbf9098c67c224d63cec3e1e1110b3a76001bcb6b4b8e456f994d42c3" } } ], "extra": [ 1, 87, 145, 89, 51, 26, 248, 9, 211, 178, 54, 68, 174, 192, 191, 56, 31, 80, 178, 45, 177, 91, 84, 129, 111, 227, 133, 154, 175, 141, 174, 160, 133, 2, 17, 0, 0, 1, 237, 223, 30, 72, 187, 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