Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f5e04d921fee10fe4ce0680ee6b9985193a7cbba7c65fc2cb911b9fdcbae221

Tx prefix hash: d46fac886aef1780f5126697f53ec78e66833105fde3c850b8d19196d3326fa2
Tx public key: 3c1739448ef719749a1f8f5419bc9fd8e37d4ce9d93cbc1df8c9c731009a4c5b
Timestamp: 1744863913 Timestamp [UTC]: 2025-04-17 04:25:13 Age [y:d:h:m:s]: 01:212:01:26:26
Block: 1263172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415510 RingCT/type: yes/0
Extra: 013c1739448ef719749a1f8f5419bc9fd8e37d4ce9d93cbc1df8c9c731009a4c5b021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ea74fc10bbe48b3da4b01c1e5d45c6957f9da3a1b5d043937e252db6438cbad 0.000600000000 1750357 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": 1263182, "vin": [ { "gen": { "height": 1263172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ea74fc10bbe48b3da4b01c1e5d45c6957f9da3a1b5d043937e252db6438cbad" } } ], "extra": [ 1, 60, 23, 57, 68, 142, 247, 25, 116, 154, 31, 143, 84, 25, 188, 159, 216, 227, 125, 76, 233, 217, 60, 188, 29, 248, 201, 199, 49, 0, 154, 76, 91, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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: