Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c52a5e10b0630c57230c5dc5d711298cb3b84e49a5ac4009e41e3e25b450b286

Tx prefix hash: 5be8ca32d96804d6d19710b57f862c9a4d983a119a6ece2fc8884a335443afda
Tx public key: 77a4ae2adb7be2980659647b2827d4e57af46e126bfdee50d8208ea3773fb42a
Timestamp: 1580703811 Timestamp [UTC]: 2020-02-03 04:23:31 Age [y:d:h:m:s]: 06:293:18:47:52
Block: 57751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1625743 RingCT/type: yes/0
Extra: 0177a4ae2adb7be2980659647b2827d4e57af46e126bfdee50d8208ea3773fb42a021100000001ff58ae94000000000000000000

1 output(s) for total of 0.395046105787 xmr

stealth address amount amount idx tag
00: 1cfc2baa52f6e216c4bf3e125ea6dbccef309415894d54b20b0ffa67c95bd0a9 0.395046105787 106714 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": 57761, "vin": [ { "gen": { "height": 57751 } } ], "vout": [ { "amount": 395046105787, "target": { "key": "1cfc2baa52f6e216c4bf3e125ea6dbccef309415894d54b20b0ffa67c95bd0a9" } } ], "extra": [ 1, 119, 164, 174, 42, 219, 123, 226, 152, 6, 89, 100, 123, 40, 39, 212, 229, 122, 244, 110, 18, 107, 253, 238, 80, 216, 32, 142, 163, 119, 63, 180, 42, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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: