Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44e121bcb3a913a58198d0e7636fb2b3595a2708ed4d331383b9587203301b17

Tx prefix hash: c6e91be641f212a22dce6b0d6b8a1204c2b14127a2acefb93b43ab0613761c2e
Tx public key: 01dc63721166495f74e6f62ed4d604c7fa800d0e0188724d0190bd0ee3b0320a
Timestamp: 1711260009 Timestamp [UCT]: 2024-03-24 06:00:09 Age [y:d:h:m:s]: 01:014:00:07:49
Block: 985115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270955 RingCT/type: yes/0
Extra: 0101dc63721166495f74e6f62ed4d604c7fa800d0e0188724d0190bd0ee3b0320a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40f0c8bc1d0f9264af8fa3f62071c8dea9f5bf1247f0fad0b1f7564d05836cdc 0.600000000000 1445322 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": 985125, "vin": [ { "gen": { "height": 985115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40f0c8bc1d0f9264af8fa3f62071c8dea9f5bf1247f0fad0b1f7564d05836cdc" } } ], "extra": [ 1, 1, 220, 99, 114, 17, 102, 73, 95, 116, 230, 246, 46, 212, 214, 4, 199, 250, 128, 13, 14, 1, 136, 114, 77, 1, 144, 189, 14, 227, 176, 50, 10, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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