Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dfa3d8a2ed97620dc35dd5183cb418650da79ac960262300169342ab3aa776e

Tx prefix hash: 808f81c1cc61012cfbe90ce90707ce195b99846c036849722271d545d2a4d987
Tx public key: 05b3e38cbcb1320774d36e8def9e2a17fb669df22947486a0f248efb1231fc3a
Timestamp: 1725192235 Timestamp [UTC]: 2024-09-01 12:03:55 Age [y:d:h:m:s]: 02:079:07:24:42
Block: 1100606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581497 RingCT/type: yes/0
Extra: 0105b3e38cbcb1320774d36e8def9e2a17fb669df22947486a0f248efb1231fc3a021100000005e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9a2f0e2131654d602b601f061d9087f26149b8a0a82444a0619f840b1512bc26 0.000600000000 1576585 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": 1100616, "vin": [ { "gen": { "height": 1100606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a2f0e2131654d602b601f061d9087f26149b8a0a82444a0619f840b1512bc26" } } ], "extra": [ 1, 5, 179, 227, 140, 188, 177, 50, 7, 116, 211, 110, 141, 239, 158, 42, 23, 251, 102, 157, 242, 41, 71, 72, 106, 15, 36, 142, 251, 18, 49, 252, 58, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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: