Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6350596ea15cdd71c9f4a4d93bf245759b9edc0542a740b99dabf89d498ff7e2

Tx prefix hash: 9747bd613ea27ecfaa41accd8a66625abf28c615be3ed3f4994cd6dbd68d8942
Tx public key: 674e7ba3fbb7013a68bea7969fafc7da0bbe4305000728a7c79274d6aab1969b
Timestamp: 1742742218 Timestamp [UTC]: 2025-03-23 15:03:38 Age [y:d:h:m:s]: 01:244:02:44:45
Block: 1245630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437864 RingCT/type: yes/0
Extra: 01674e7ba3fbb7013a68bea7969fafc7da0bbe4305000728a7c79274d6aab1969b02110000000324ff4ea1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 293df12e0929519800071a5b02d941e87fe0a259e2c7e035a1adf35d9901794f 0.000600000000 1732621 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": 1245640, "vin": [ { "gen": { "height": 1245630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "293df12e0929519800071a5b02d941e87fe0a259e2c7e035a1adf35d9901794f" } } ], "extra": [ 1, 103, 78, 123, 163, 251, 183, 1, 58, 104, 190, 167, 150, 159, 175, 199, 218, 11, 190, 67, 5, 0, 7, 40, 167, 199, 146, 116, 214, 170, 177, 150, 155, 2, 17, 0, 0, 0, 3, 36, 255, 78, 161, 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: