Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77973eeee0e81f9e5d1310617ea7e00eb5d14ee5dfe42927baab7cb78c40bd9f

Tx prefix hash: 84636a518b6a2a4c55798a0e77b17ebdd86d7020a3b8f68c76f23f1df82fd5e7
Tx public key: 737ab345228d34eba0ac0d2f2259051e5e90479843e9ef82c4756be7c3000935
Timestamp: 1574745159 Timestamp [UCT]: 2019-11-26 05:12:39 Age [y:d:h:m:s]: 05:338:10:40:36
Block: 17667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1382218 RingCT/type: yes/0
Extra: 01737ab345228d34eba0ac0d2f2259051e5e90479843e9ef82c4756be7c3000935021100000001f95225a5000000000000000000

1 output(s) for total of 536.367895781000 dcy

stealth address amount amount idx
00: 687d27f361009b98afb48a2334f383ed4ab1d6bfbac7c5e9b18852a67c9b1c55 536.367895781000 26011 of 0

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": 17677, "vin": [ { "gen": { "height": 17667 } } ], "vout": [ { "amount": 536367895781, "target": { "key": "687d27f361009b98afb48a2334f383ed4ab1d6bfbac7c5e9b18852a67c9b1c55" } } ], "extra": [ 1, 115, 122, 179, 69, 34, 141, 52, 235, 160, 172, 13, 47, 34, 89, 5, 30, 94, 144, 71, 152, 67, 233, 239, 130, 196, 117, 107, 231, 195, 0, 9, 53, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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