Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 231a9a684732fe37f8dbc4bac069cf5ff7e9865fc51d5aab2e5bc0f5d11347a5

Tx prefix hash: 6eab870611049789c667aa501183f4f9f6d8b8fe62eec3507c6a54736ab51b69
Tx public key: 315d9dd099e4f832684a04f38551bf3bb0f34fd3c7094af7daa59e36f3bdd2cf
Timestamp: 1636006591 Timestamp [UCT]: 2021-11-04 06:16:31 Age [y:d:h:m:s]: 03:226:06:00:58
Block: 366989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 939961 RingCT/type: yes/0
Extra: 01315d9dd099e4f832684a04f38551bf3bb0f34fd3c7094af7daa59e36f3bdd2cf021100000014745f00f8000000000000000000

1 output(s) for total of 37.329075812000 dcy

stealth address amount amount idx
00: c0e618840d271c28b87157a2594e2c6c32c5b8fad465bceaa7d4c3a3c3dd7d81 37.329075812000 744775 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": 366999, "vin": [ { "gen": { "height": 366989 } } ], "vout": [ { "amount": 37329075812, "target": { "key": "c0e618840d271c28b87157a2594e2c6c32c5b8fad465bceaa7d4c3a3c3dd7d81" } } ], "extra": [ 1, 49, 93, 157, 208, 153, 228, 248, 50, 104, 74, 4, 243, 133, 81, 191, 59, 176, 243, 79, 211, 199, 9, 74, 247, 218, 165, 158, 54, 243, 189, 210, 207, 2, 17, 0, 0, 0, 20, 116, 95, 0, 248, 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