Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68030df675bbb8eb0b8a5ea9be3b510f839c864fb7e1ec3080f5f7e80cb7abac

Tx prefix hash: e0e58685726a6c8445087e3eba4b3d7d8b413e6f63cf0ad427c4001be1393d4f
Tx public key: 5748a7c1047c61b17354c3672921fba6c35afce95c46553c84c8aedbb654d93d
Timestamp: 1775159233 Timestamp [UTC]: 2026-04-02 19:47:13 Age [y:d:h:m:s]: 00:230:04:27:10
Block: 1511438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170060 RingCT/type: yes/0
Extra: 015748a7c1047c61b17354c3672921fba6c35afce95c46553c84c8aedbb654d93d021100000003ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 49148610b9323eba44719d7c5a70f8332369ea934c6c1a63bdc6434492c48967 0.000600000000 2001230 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": 1511448, "vin": [ { "gen": { "height": 1511438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49148610b9323eba44719d7c5a70f8332369ea934c6c1a63bdc6434492c48967" } } ], "extra": [ 1, 87, 72, 167, 193, 4, 124, 97, 177, 115, 84, 195, 103, 41, 33, 251, 166, 195, 90, 252, 233, 92, 70, 85, 60, 132, 200, 174, 219, 182, 84, 217, 61, 2, 17, 0, 0, 0, 3, 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: