Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07679d7ecafb612097e0302dd157a974f5b576dc8c3d0260b03b14ddd155bada

Tx prefix hash: 760f51762aeb2634f3209db7d163de29abd6c9abab8a240da7c2001396307a65
Tx public key: cfaa36905151e8f06a6febbd382e1c6870ff8d1eeae3d74f1cc1f5ab69a35546
Timestamp: 1710407380 Timestamp [UCT]: 2024-03-14 09:09:40 Age [y:d:h:m:s]: 01:240:07:24:17
Block: 978044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430448 RingCT/type: yes/0
Extra: 01cfaa36905151e8f06a6febbd382e1c6870ff8d1eeae3d74f1cc1f5ab69a355460211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9594167a2aa733797612b2f3d8fccf0c7be55e6b4ec09b61ff03d7f34c502b8 0.600000000000 1438061 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": 978054, "vin": [ { "gen": { "height": 978044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9594167a2aa733797612b2f3d8fccf0c7be55e6b4ec09b61ff03d7f34c502b8" } } ], "extra": [ 1, 207, 170, 54, 144, 81, 81, 232, 240, 106, 111, 235, 189, 56, 46, 28, 104, 112, 255, 141, 30, 234, 227, 215, 79, 28, 193, 245, 171, 105, 163, 85, 70, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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