Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e149dacdda67f41b8e03de53980f4a057050d778cc6cbefce545349c7f9d4b

Tx prefix hash: 28645b2abfa8a1e594f225bab584c6c45b806c99f2bade04f35b608566a257d5
Tx public key: 593131c58a75e580330d4a1df9831cef869f892d5bb69c150323be147c31e393
Timestamp: 1735122560 Timestamp [UCT]: 2024-12-25 10:29:20 Age [y:d:h:m:s]: 00:099:14:24:40
Block: 1182814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70967 RingCT/type: yes/0
Extra: 01593131c58a75e580330d4a1df9831cef869f892d5bb69c150323be147c31e3930211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40be64fdf8903ee6fa0c706716e14b3d4eb2fa3a8e2c59337d3e8959c4e81e8a 0.600000000000 1669253 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": 1182824, "vin": [ { "gen": { "height": 1182814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40be64fdf8903ee6fa0c706716e14b3d4eb2fa3a8e2c59337d3e8959c4e81e8a" } } ], "extra": [ 1, 89, 49, 49, 197, 138, 117, 229, 128, 51, 13, 74, 29, 249, 131, 28, 239, 134, 159, 137, 45, 91, 182, 156, 21, 3, 35, 190, 20, 124, 49, 227, 147, 2, 17, 0, 0, 0, 2, 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