Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39263e2c52fac51a08f29f720f53f4be23163fcedfd32008e36a5131b70c9875

Tx prefix hash: 4dbe2884df3f283da56da7ac199f28b77ef93ffa16aa8c1654be7250c056b0e3
Tx public key: 03826d36e49b7bac60cc081237f288e8a778b0e42bd449d06d89488079226c85
Timestamp: 1705420319 Timestamp [UTC]: 2024-01-16 15:51:59 Age [y:d:h:m:s]: 02:116:11:09:28
Block: 936665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595122 RingCT/type: yes/0
Extra: 0103826d36e49b7bac60cc081237f288e8a778b0e42bd449d06d89488079226c850211000000080011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 68ba0fd19768b303b2b68d7c4c254990e9680d1f6d4ccceeefab7997b833aff3 0.000600000000 1394703 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": 936675, "vin": [ { "gen": { "height": 936665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68ba0fd19768b303b2b68d7c4c254990e9680d1f6d4ccceeefab7997b833aff3" } } ], "extra": [ 1, 3, 130, 109, 54, 228, 155, 123, 172, 96, 204, 8, 18, 55, 242, 136, 232, 167, 120, 176, 228, 43, 212, 73, 208, 109, 137, 72, 128, 121, 34, 108, 133, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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: