Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc4640b846674f1f63bfbeff25233434e2c9192892dc029529ca41c6ed2ee6a

Tx prefix hash: cce6ca0d833c9c5d6a71ca33d9652dc616e670c1dd79133c3e6bff065ff2caeb
Tx public key: 75c236297b8d7377c01cbf791dd2728dde835205a2f598e5b3d2146908d9c8e5
Timestamp: 1746218849 Timestamp [UCT]: 2025-05-02 20:47:29 Age [y:d:h:m:s]: 00:200:02:24:05
Block: 1274399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140724 RingCT/type: yes/0
Extra: 0175c236297b8d7377c01cbf791dd2728dde835205a2f598e5b3d2146908d9c8e50211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8c41ed6bc8777422d615ec2369f3a1687e29f60f5ab5dac81664f763c09d543 0.600000000000 1761694 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": 1274409, "vin": [ { "gen": { "height": 1274399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8c41ed6bc8777422d615ec2369f3a1687e29f60f5ab5dac81664f763c09d543" } } ], "extra": [ 1, 117, 194, 54, 41, 123, 141, 115, 119, 192, 28, 191, 121, 29, 210, 114, 141, 222, 131, 82, 5, 162, 245, 152, 229, 179, 210, 20, 105, 8, 217, 200, 229, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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