Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd49e1dfed3c23e4abccf6b6d0e1d1f6dcf17d3eb1bc2e9d0267692b545f08f

Tx prefix hash: 9179f2df794d8648e64bbdac9915f1b74ade52c3aa6f6fff3f5b958c841eb2c2
Tx public key: a5761f8bf3b94380f869fd7aab159ffb1b21b8a431aee3a3c00982445c817887
Timestamp: 1744460793 Timestamp [UTC]: 2025-04-12 12:26:33 Age [y:d:h:m:s]: 01:216:04:02:34
Block: 1259845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418414 RingCT/type: yes/0
Extra: 01a5761f8bf3b94380f869fd7aab159ffb1b21b8a431aee3a3c00982445c8178870211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bafb352d851caf97bd54afd8d2a53ac1054f42a662c98ce81113e6e7da7c742e 0.000600000000 1746994 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": 1259855, "vin": [ { "gen": { "height": 1259845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bafb352d851caf97bd54afd8d2a53ac1054f42a662c98ce81113e6e7da7c742e" } } ], "extra": [ 1, 165, 118, 31, 139, 243, 185, 67, 128, 248, 105, 253, 122, 171, 21, 159, 251, 27, 33, 184, 164, 49, 174, 227, 163, 192, 9, 130, 68, 92, 129, 120, 135, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: