Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbcde328492c63f1ab82f205f287968745d8450f742f0bded47d4f7d66264b24

Tx prefix hash: 96784aeae088c787e07f9c5ef6a78b4affe17aff97e047457dd1d78be1b09d31
Tx public key: 7e2ae2345711a7fdc52eb03b36e485fe14fdf54081bc21e5a12c40334904b0c0
Timestamp: 1721136192 Timestamp [UCT]: 2024-07-16 13:23:12 Age [y:d:h:m:s]: 00:265:00:02:09
Block: 1066990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189297 RingCT/type: yes/0
Extra: 017e2ae2345711a7fdc52eb03b36e485fe14fdf54081bc21e5a12c40334904b0c002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0cd0e8b11c308d082750a7822b552882bd3678500ec4572b944520530dba562 0.600000000000 1537683 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": 1067000, "vin": [ { "gen": { "height": 1066990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0cd0e8b11c308d082750a7822b552882bd3678500ec4572b944520530dba562" } } ], "extra": [ 1, 126, 42, 226, 52, 87, 17, 167, 253, 197, 46, 176, 59, 54, 228, 133, 254, 20, 253, 245, 64, 129, 188, 33, 229, 161, 44, 64, 51, 73, 4, 176, 192, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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