Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a860d6f11ea0e5d269367386617b986749fc37eaacb732179e166499afc549

Tx prefix hash: 83941d537c661266d79b186f4d6b08608d412dcb73472b6d53f3e08efb213926
Tx public key: fc72beea1c2fb96237085673cde115f52e481a84099fbcfce0a8908fe7b8cf01
Timestamp: 1713557891 Timestamp [UCT]: 2024-04-19 20:18:11 Age [y:d:h:m:s]: 01:196:15:21:25
Block: 1004130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399200 RingCT/type: yes/0
Extra: 01fc72beea1c2fb96237085673cde115f52e481a84099fbcfce0a8908fe7b8cf0102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb6cb145a66bc5309504da7f2a3c0e8c7040f63700b49f48f4909b8e3a864264 0.600000000000 1464698 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": 1004140, "vin": [ { "gen": { "height": 1004130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb6cb145a66bc5309504da7f2a3c0e8c7040f63700b49f48f4909b8e3a864264" } } ], "extra": [ 1, 252, 114, 190, 234, 28, 47, 185, 98, 55, 8, 86, 115, 205, 225, 21, 245, 46, 72, 26, 132, 9, 159, 188, 252, 224, 168, 144, 143, 231, 184, 207, 1, 2, 17, 0, 0, 0, 4, 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