Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41028a17224249ecce58a09a5b53c7459fdfebb8c7e7b598d930b7f0e5b3087d

Tx prefix hash: 935a956523bcb2f643df5480a43e291975de319119811328499b5e4b2d73df78
Tx public key: f7a7a1b6bdde43cd644af9c88ace0d4910a4dbaf6d6c171bf041baa59f36bb62
Timestamp: 1728992196 Timestamp [UCT]: 2024-10-15 11:36:36 Age [y:d:h:m:s]: 00:102:20:14:44
Block: 1132110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73467 RingCT/type: yes/0
Extra: 01f7a7a1b6bdde43cd644af9c88ace0d4910a4dbaf6d6c171bf041baa59f36bb62021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67c9338b0f591f6120d333bcf929f552210b245d948eb2e1f82d462048529528 0.600000000000 1615023 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": 1132120, "vin": [ { "gen": { "height": 1132110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67c9338b0f591f6120d333bcf929f552210b245d948eb2e1f82d462048529528" } } ], "extra": [ 1, 247, 167, 161, 182, 189, 222, 67, 205, 100, 74, 249, 200, 138, 206, 13, 73, 16, 164, 219, 175, 109, 108, 23, 27, 240, 65, 186, 165, 159, 54, 187, 98, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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