Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaa16340c130de03377a8a7157c6ea36cf132a8e6e801a63b349a929e03adb03

Tx prefix hash: 526e0f1cdf3bc1c866645726c910c6bcffe0dbff51ed799a97350c470f3a9c62
Tx public key: e01fe5f0ec0ea3df0f21772724d605c68f72ff96bc12b2b182b821955180ae2c
Timestamp: 1719103655 Timestamp [UCT]: 2024-06-23 00:47:35 Age [y:d:h:m:s]: 00:361:11:02:57
Block: 1050106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258219 RingCT/type: yes/0
Extra: 01e01fe5f0ec0ea3df0f21772724d605c68f72ff96bc12b2b182b821955180ae2c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72e2e04115de9afa27ec117e9c2057b6c1285d11547cf045dee8bc18f08f9925 0.600000000000 1520263 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": 1050116, "vin": [ { "gen": { "height": 1050106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72e2e04115de9afa27ec117e9c2057b6c1285d11547cf045dee8bc18f08f9925" } } ], "extra": [ 1, 224, 31, 229, 240, 236, 14, 163, 223, 15, 33, 119, 39, 36, 214, 5, 198, 143, 114, 255, 150, 188, 18, 178, 177, 130, 184, 33, 149, 81, 128, 174, 44, 2, 17, 0, 0, 0, 1, 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