Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48a96bd8031e8ff7caf4d3953fb5eb2c49b060c823e23f3dce101daeb7ac401c

Tx prefix hash: bf4a31cde9604eb0ab651031acda048c78b777f65e45a0c85ba19a22b41c698d
Tx public key: 3c3f7c3982c24fcf1803d01406dcb541e5a9d1389e21a9eff8b0f1e44ec3e87f
Timestamp: 1781375102 Timestamp [UTC]: 2026-06-13 18:25:02 Age [y:d:h:m:s]: 00:157:12:34:20
Block: 1558493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 122464 RingCT/type: yes/0
Extra: 013c3f7c3982c24fcf1803d01406dcb541e5a9d1389e21a9eff8b0f1e44ec3e87f

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3f89e0de32d08088a98751f7c8d43964c6d89a40bf627c582c325ec5468d85fc 0.000600000000 2048471 of 15 <1d>

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": 1558503, "vin": [ { "gen": { "height": 1558493 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "3f89e0de32d08088a98751f7c8d43964c6d89a40bf627c582c325ec5468d85fc", "view_tag": "1d" } } } ], "extra": [ 1, 60, 63, 124, 57, 130, 194, 79, 207, 24, 3, 208, 20, 6, 220, 181, 65, 229, 169, 209, 56, 158, 33, 169, 239, 248, 176, 241, 228, 78, 195, 232, 127 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: