Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855c4f7eddbd6e647dd010506948535326caafa2eab9f4e3def26a30091ce5f7

Tx prefix hash: 692f59f59242451b9c903d7b160917a45845336adab01765828159373c703ad7
Tx public key: a2a79a24492540c46741128e734c35f754abb0e7facf0aa7dafca3cf546cc964
Timestamp: 1743333735 Timestamp [UTC]: 2025-03-30 11:22:15 Age [y:d:h:m:s]: 01:236:20:37:10
Block: 1250506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432988 RingCT/type: yes/0
Extra: 01a2a79a24492540c46741128e734c35f754abb0e7facf0aa7dafca3cf546cc9640211000000021a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 63cfdaa760b4c32c714236f1293dfde0c6fd8b9c10a041fcfdfffb08ae2d600e 0.000600000000 1737555 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 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": 1250516, "vin": [ { "gen": { "height": 1250506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63cfdaa760b4c32c714236f1293dfde0c6fd8b9c10a041fcfdfffb08ae2d600e" } } ], "extra": [ 1, 162, 167, 154, 36, 73, 37, 64, 196, 103, 65, 18, 142, 115, 76, 53, 247, 84, 171, 176, 231, 250, 207, 10, 167, 218, 252, 163, 207, 84, 108, 201, 100, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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: