Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3771e4780d702a4cce6b206f788daa09489c6a9ff09262aa3cbdf79b833ce9d4

Tx prefix hash: 6a5a7cfc9fc560aac0ffa30a7f5a965bae445d6a485e0de0f85afe7f00e9fe27
Tx public key: 93e97c1847f914716fd52f56d9c4ddb4f61229b1d319d1ad0cfea14559f64c6a
Timestamp: 1743802287 Timestamp [UTC]: 2025-04-04 21:31:27 Age [y:d:h:m:s]: 01:226:20:55:25
Block: 1254387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426171 RingCT/type: yes/0
Extra: 0193e97c1847f914716fd52f56d9c4ddb4f61229b1d319d1ad0cfea14559f64c6a02110000000c4060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1dcf1a80725835393b6bfff8dac771ae3705b97a3d0adc84df747bbba2fa55fb 0.000600000000 1741468 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": 1254397, "vin": [ { "gen": { "height": 1254387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dcf1a80725835393b6bfff8dac771ae3705b97a3d0adc84df747bbba2fa55fb" } } ], "extra": [ 1, 147, 233, 124, 24, 71, 249, 20, 113, 111, 213, 47, 86, 217, 196, 221, 180, 246, 18, 41, 177, 211, 25, 209, 173, 12, 254, 161, 69, 89, 246, 76, 106, 2, 17, 0, 0, 0, 12, 64, 96, 246, 210, 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: