Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c4fd948f3cd78624666c5d7bdd4bee9abc603ca593c24041c3aa72d4b61062a

Tx prefix hash: 15d5f5c04da798d6a1913041a2bdc5cff551bb83f255f3fee50912d9129d9c98
Tx public key: b5236c26d3cd64a94a92422b16652ee260a570284240dd12aa51865924f8116f
Timestamp: 1744404344 Timestamp [UTC]: 2025-04-11 20:45:44 Age [y:d:h:m:s]: 01:029:05:08:46
Block: 1259379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272150 RingCT/type: yes/0
Extra: 01b5236c26d3cd64a94a92422b16652ee260a570284240dd12aa51865924f8116f021100000005dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 016ef2dc318551ff14d7e9872824b0ee959a170d543317c45dd174f4dabaceef 0.000600000000 1746518 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": 1259389, "vin": [ { "gen": { "height": 1259379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "016ef2dc318551ff14d7e9872824b0ee959a170d543317c45dd174f4dabaceef" } } ], "extra": [ 1, 181, 35, 108, 38, 211, 205, 100, 169, 74, 146, 66, 43, 22, 101, 46, 226, 96, 165, 112, 40, 66, 64, 221, 18, 170, 81, 134, 89, 36, 248, 17, 111, 2, 17, 0, 0, 0, 5, 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: