Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c49fdc4cb814db2bdce48e0d1eed6847b04203456a3007ba84cb263b823fbec4

Tx prefix hash: 95c1aa09b8da3c0cf5e33267f5f8a4a07673e554a6388ff1d540f2e328146892
Tx public key: e93db2b3a2d1f219447ee5e440afbb5a9696aacd7de77bbc6e0a1b4b952fa505
Timestamp: 1713804738 Timestamp [UCT]: 2024-04-22 16:52:18 Age [y:d:h:m:s]: 00:151:21:21:02
Block: 1006193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108802 RingCT/type: yes/0
Extra: 01e93db2b3a2d1f219447ee5e440afbb5a9696aacd7de77bbc6e0a1b4b952fa50502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d71ed15e176c5f59df40b61d8ac1c6643ef2196ca64d59e28f7433f130b6982b 0.600000000000 1467135 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": 1006203, "vin": [ { "gen": { "height": 1006193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d71ed15e176c5f59df40b61d8ac1c6643ef2196ca64d59e28f7433f130b6982b" } } ], "extra": [ 1, 233, 61, 178, 179, 162, 209, 242, 25, 68, 126, 229, 228, 64, 175, 187, 90, 150, 150, 170, 205, 125, 231, 123, 188, 110, 10, 27, 75, 149, 47, 165, 5, 2, 17, 0, 0, 0, 1, 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