Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df7a0b3e8a30d60b8ce06605407fb3c20a9ef7e39d9a2fa75c5ff90a07d6be5a

Tx prefix hash: 1a4a5d978f909671c166c7567da3bbceba5625e1223e8cc349e20d27d327f1a0
Tx public key: d2dd331a74de4682a4fd2c10e6a91723dba43aff596f142bcc5cafec4bf9648d
Timestamp: 1775031939 Timestamp [UTC]: 2026-04-01 08:25:39 Age [y:d:h:m:s]: 00:232:09:07:47
Block: 1510391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171651 RingCT/type: yes/0
Extra: 01d2dd331a74de4682a4fd2c10e6a91723dba43aff596f142bcc5cafec4bf9648d02110000000dee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b7ea6efcad4b0b163582bca544047e45c5b8f65e931e9983d47a75932c6d165d 0.000600000000 2000175 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": 1510401, "vin": [ { "gen": { "height": 1510391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ea6efcad4b0b163582bca544047e45c5b8f65e931e9983d47a75932c6d165d" } } ], "extra": [ 1, 210, 221, 51, 26, 116, 222, 70, 130, 164, 253, 44, 16, 230, 169, 23, 35, 219, 164, 58, 255, 89, 111, 20, 43, 204, 92, 175, 236, 75, 249, 100, 141, 2, 17, 0, 0, 0, 13, 238, 75, 113, 129, 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: