Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a389e4e651f674abd514e387511380ef4fe0b46a5529401c40e28f4aa10a51

Tx prefix hash: cdfecd4f6fb6fa935e5250f84c933a446457c0de296a492503404f51d3550dfb
Tx public key: c218f44508e71118cccf61194c3b36ef35757600c87d7e832d511e9dd6f71993
Timestamp: 1738517672 Timestamp [UTC]: 2025-02-02 17:34:32 Age [y:d:h:m:s]: 01:292:11:48:51
Block: 1210636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472858 RingCT/type: yes/0
Extra: 01c218f44508e71118cccf61194c3b36ef35757600c87d7e832d511e9dd6f7199302110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b257df566b8980233e8296ec7af90cad34cc1b51ee8b24884d0ba8c2e7af376 0.000600000000 1697389 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": 1210646, "vin": [ { "gen": { "height": 1210636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b257df566b8980233e8296ec7af90cad34cc1b51ee8b24884d0ba8c2e7af376" } } ], "extra": [ 1, 194, 24, 244, 69, 8, 231, 17, 24, 204, 207, 97, 25, 76, 59, 54, 239, 53, 117, 118, 0, 200, 125, 126, 131, 45, 81, 30, 157, 214, 247, 25, 147, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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: