Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e249a5adb4d046d4ef43e3183df877761e9a392fb99b7995ccbf278d9ff5af

Tx prefix hash: d8c9f433c4ce311dd4fe9518bd2a3002ad72d1a361752b7b40e7d0ae388b0735
Tx public key: 5dae4c3a9bf0c0bb60dfc40182578e71a70096bd4b81e8621048bf5f51e28829
Timestamp: 1579943834 Timestamp [UTC]: 2020-01-25 09:17:14 Age [y:d:h:m:s]: 06:302:21:12:18
Block: 52503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1630991 RingCT/type: yes/0
Extra: 015dae4c3a9bf0c0bb60dfc40182578e71a70096bd4b81e8621048bf5f51e288290211000000012264afe6000000000000000000

1 output(s) for total of 0.411196307583 xmr

stealth address amount amount idx tag
00: b0cb469581d11a3b87692874c47d286b69361dc5281e60df77d0413e1d2018a9 0.411196307583 97326 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 dinastycoin-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": 52513, "vin": [ { "gen": { "height": 52503 } } ], "vout": [ { "amount": 411196307583, "target": { "key": "b0cb469581d11a3b87692874c47d286b69361dc5281e60df77d0413e1d2018a9" } } ], "extra": [ 1, 93, 174, 76, 58, 155, 240, 192, 187, 96, 223, 196, 1, 130, 87, 142, 113, 167, 0, 150, 189, 75, 129, 232, 98, 16, 72, 191, 95, 81, 226, 136, 41, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: