Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d34e7d5b84bc46b2ad51221f17091b5af477b8e051d677cbad08fdc0ff17bde

Tx prefix hash: a4943a8d9390aea13d89319af013b8dc1b906f7c7534cfd6b2ac32ab416f555e
Tx public key: 568e86ea83f487eda92422a16ad52a9f8ad47d9dd57c88afe3587349aa20b61d
Timestamp: 1716078279 Timestamp [UCT]: 2024-05-19 00:24:39 Age [y:d:h:m:s]: 00:323:14:59:19
Block: 1025044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231306 RingCT/type: yes/0
Extra: 01568e86ea83f487eda92422a16ad52a9f8ad47d9dd57c88afe3587349aa20b61d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9e4e31d4e98cffa5415fdb661eaf8b18810a9464cea3f24552972b86875d3ca 0.600000000000 1491255 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": 1025054, "vin": [ { "gen": { "height": 1025044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9e4e31d4e98cffa5415fdb661eaf8b18810a9464cea3f24552972b86875d3ca" } } ], "extra": [ 1, 86, 142, 134, 234, 131, 244, 135, 237, 169, 36, 34, 161, 106, 213, 42, 159, 138, 212, 125, 157, 213, 124, 136, 175, 227, 88, 115, 73, 170, 32, 182, 29, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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