Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5017e723365476573ec28d535c7b406c1d9818eb7096b47ceaba1e91b3e39cc6

Tx prefix hash: 322a80d9822395d7ae3f8f8fcd7fa0e805dcd83025e776194537517fad7a6b18
Tx public key: ae097cad1bff819a42ec5cb3ed17f153a7f1e26100f42d7d131c36429b2f18f2
Timestamp: 1728195254 Timestamp [UCT]: 2024-10-06 06:14:14 Age [y:d:h:m:s]: 00:185:05:45:19
Block: 1125497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132193 RingCT/type: yes/0
Extra: 01ae097cad1bff819a42ec5cb3ed17f153a7f1e26100f42d7d131c36429b2f18f202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb442aec325b99c88e0e40c820b0b72888d129dede51b68ca2bb318fa7fbc597 0.600000000000 1608248 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": 1125507, "vin": [ { "gen": { "height": 1125497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb442aec325b99c88e0e40c820b0b72888d129dede51b68ca2bb318fa7fbc597" } } ], "extra": [ 1, 174, 9, 124, 173, 27, 255, 129, 154, 66, 236, 92, 179, 237, 23, 241, 83, 167, 241, 226, 97, 0, 244, 45, 125, 19, 28, 54, 66, 155, 47, 24, 242, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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