Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 748d6638ae24bb390898c277c23bcdd2506f3f13039e1e2f04319044d5a27ea9

Tx prefix hash: 127980eac6e500d54e163f7e601a66c13ed590319896c729fabd08fac608eb78
Tx public key: a5c4ebd0a1e780303c8bdf41d259ad53469dea43a98a70792e739572779e21e5
Timestamp: 1574470779 Timestamp [UTC]: 2019-11-23 00:59:39 Age [y:d:h:m:s]: 06:302:23:18:16
Block: 14898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1624356 RingCT/type: yes/0
Extra: 01a5c4ebd0a1e780303c8bdf41d259ad53469dea43a98a70792e739572779e21e50211000000050b4dd45a000000000000000000

1 output(s) for total of 0.547831554901 xmr

stealth address amount amount idx tag
00: 7ca5b8e3bc19773bf2c8a275e8a09606f0646f26263af818f1f74b672ef77fa4 0.547831554901 19423 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": 14908, "vin": [ { "gen": { "height": 14898 } } ], "vout": [ { "amount": 547831554901, "target": { "key": "7ca5b8e3bc19773bf2c8a275e8a09606f0646f26263af818f1f74b672ef77fa4" } } ], "extra": [ 1, 165, 196, 235, 208, 161, 231, 128, 48, 60, 139, 223, 65, 210, 89, 173, 83, 70, 157, 234, 67, 169, 138, 112, 121, 46, 115, 149, 114, 119, 158, 33, 229, 2, 17, 0, 0, 0, 5, 11, 77, 212, 90, 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: