Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd339eb3be8c666ff1d3c890e9f5333e258e295dd3488d7bab6a33efc4a3f414

Tx prefix hash: 054ef6631c2411b230faf9ed3d5c2fa0ee5a3f29fcc48948b65b0f63710be521
Tx public key: 7e117226a912cf09c881093ec7045bdf453acb41b4cd93bb03a93dff80a9af2d
Timestamp: 1732228430 Timestamp [UCT]: 2024-11-21 22:33:50 Age [y:d:h:m:s]: 00:114:10:15:48
Block: 1158841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81606 RingCT/type: yes/0
Extra: 017e117226a912cf09c881093ec7045bdf453acb41b4cd93bb03a93dff80a9af2d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57a508acba620f38e52aa468f75b659c582e3dc88c1e46939ae7a21009c1d785 0.600000000000 1644470 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": 1158851, "vin": [ { "gen": { "height": 1158841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57a508acba620f38e52aa468f75b659c582e3dc88c1e46939ae7a21009c1d785" } } ], "extra": [ 1, 126, 17, 114, 38, 169, 18, 207, 9, 200, 129, 9, 62, 199, 4, 91, 223, 69, 58, 203, 65, 180, 205, 147, 187, 3, 169, 61, 255, 128, 169, 175, 45, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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