Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af831d818d7997b2a95effe62af3e01e52859bb0da6e2a66a3e36b59668ed87a

Tx prefix hash: 2c8e69e7ae69ca7e9ec8fe473721387e9b2feedb4ad5d90f4a270f3dbb8990dd
Tx public key: abe311a3738b0cb95513ac250f0a154711aee082dd28aafc7c1128029ee9d7ac
Timestamp: 1730913421 Timestamp [UCT]: 2024-11-06 17:17:01 Age [y:d:h:m:s]: 00:076:15:46:59
Block: 1147950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54796 RingCT/type: yes/0
Extra: 01abe311a3738b0cb95513ac250f0a154711aee082dd28aafc7c1128029ee9d7ac0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3421ed5f1293816a011e28e6c49a71c1b8266277a7ba83e10d104ded7c0c8ea6 0.600000000000 1632671 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": 1147960, "vin": [ { "gen": { "height": 1147950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3421ed5f1293816a011e28e6c49a71c1b8266277a7ba83e10d104ded7c0c8ea6" } } ], "extra": [ 1, 171, 227, 17, 163, 115, 139, 12, 185, 85, 19, 172, 37, 15, 10, 21, 71, 17, 174, 224, 130, 221, 40, 170, 252, 124, 17, 40, 2, 158, 233, 215, 172, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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