Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be599dc152aebd8f773da7a4448bcebc2dcdd6d260a66fa4118dcb541c86cf2c

Tx prefix hash: 95fd3339fc81cf347b99229d3d92df6bc8d601a78c6a7c1d16c400e71763a4fd
Tx public key: 6bc06dabf346255543cb2a0facfaa1c74d35dab40bbb72afffe70f3fbfa0e484
Timestamp: 1741975668 Timestamp [UTC]: 2025-03-14 18:07:48 Age [y:d:h:m:s]: 01:247:14:34:54
Block: 1239292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440974 RingCT/type: yes/0
Extra: 016bc06dabf346255543cb2a0facfaa1c74d35dab40bbb72afffe70f3fbfa0e4840211000000081f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 79216cdad85242e6a77101aa549f719687ef73119a37ce5ef1a61c79de2c0d7d 0.000600000000 1726257 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": 1239302, "vin": [ { "gen": { "height": 1239292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79216cdad85242e6a77101aa549f719687ef73119a37ce5ef1a61c79de2c0d7d" } } ], "extra": [ 1, 107, 192, 109, 171, 243, 70, 37, 85, 67, 203, 42, 15, 172, 250, 161, 199, 77, 53, 218, 180, 11, 187, 114, 175, 255, 231, 15, 63, 191, 160, 228, 132, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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: