Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c599c4fde42ba10e47de27af946c4aeea9fbbd0023e29eaae4149209832363e7

Tx prefix hash: 4ff162be23b32c7328e26bebed3b59e6abfb3e7b15cf61aa0693c8a4bf4a8414
Tx public key: c583aa7882e3849a7074e8b36b3c93d50bb9e91e51c9fc29f862b609365820bb
Timestamp: 1705415502 Timestamp [UTC]: 2024-01-16 14:31:42 Age [y:d:h:m:s]: 02:310:14:37:02
Block: 936626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 746868 RingCT/type: yes/0
Extra: 01c583aa7882e3849a7074e8b36b3c93d50bb9e91e51c9fc29f862b609365820bb0211000000070011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b024f17963b7e67ed45b54bf42fa8d46b1cc0f555e03d25d72c8a450bde9596e 0.000600000000 1394660 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": 936636, "vin": [ { "gen": { "height": 936626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b024f17963b7e67ed45b54bf42fa8d46b1cc0f555e03d25d72c8a450bde9596e" } } ], "extra": [ 1, 197, 131, 170, 120, 130, 227, 132, 154, 112, 116, 232, 179, 107, 60, 147, 213, 11, 185, 233, 30, 81, 201, 252, 41, 248, 98, 182, 9, 54, 88, 32, 187, 2, 17, 0, 0, 0, 7, 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: