Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c62e0d235cbdceb099fdd3df6bdd2f0046acf916f5348e3a1c8a85f92a35c10

Tx prefix hash: f2c4cd75c12f023bc1b6cc7353950f3feac1a913b093a533ee5f388ba0fbc18e
Tx public key: 8dada43caa87826f5b501b44e839cfc59c6c7c314f222b5e0dbedeb9988f5c51
Timestamp: 1700853573 Timestamp [UCT]: 2023-11-24 19:19:33 Age [y:d:h:m:s]: 02:014:17:43:17
Block: 898827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530316 RingCT/type: yes/0
Extra: 018dada43caa87826f5b501b44e839cfc59c6c7c314f222b5e0dbedeb9988f5c51021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.645376301000 dcy

stealth address amount amount idx
00: 325f54080859b2381f3ec7381cd3b0098683c5eb2c1e53a38ff235b02ce36392 0.645376301000 1355262 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": 898837, "vin": [ { "gen": { "height": 898827 } } ], "vout": [ { "amount": 645376301, "target": { "key": "325f54080859b2381f3ec7381cd3b0098683c5eb2c1e53a38ff235b02ce36392" } } ], "extra": [ 1, 141, 173, 164, 60, 170, 135, 130, 111, 91, 80, 27, 68, 232, 57, 207, 197, 156, 108, 124, 49, 79, 34, 43, 94, 13, 190, 222, 185, 152, 143, 92, 81, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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